One of the two messages of RSPEC-3077 was not clear enough: "Remove the "volatile" keyword from this field"
Removing the volatile keyword is only part of the fix. This message is now replaced with:
"Use a thread-safe type; adding "volatile" is not enough to make this field thread-safe."
The other message, i.e. "Use an "Atomic[Reference|Integer|Long]Array" instead." is fine.