RF+MSC: switch off pickling of internal surface objects

in the current implementation this comes with a significant speed penalty. 
TODO: see if these internal surface objects can be stored more efficiently.

Note that if these objects are ignored in __reduce__, they will be regenerated upon the first call of the respective function - which comes with quite a minor speed penalty.

@hanke and @yarikoptic, what do you think?