Scala reflection, @ScalaSignature and obfuscation

Doing reflection using Scala's API gives all sorts of weird errors when the classes have been obfuscated. Somehow the reflection seems to be aware of how the classes were before the obfuscation.

I suspect the annotation @ScalaSignature contains the class-, field- and method names as they were before Proguard renamed them. I'm not sure though.

Is there a way to 'recompute' the annotation post-obfuscation ?

Or maybe tell the compiler not to include it ?

Or strip them altogether out of the classes ?