Ah yes, you're right. Maybe it's Groovy classes that this doesn't work for?

Still, when a refactoring operation doesn't exist for a code change (even if it's due to operator ignorance) it's nice to have the Problems pane to tidy up with.