Mark callback Str parameters as not to be freed

If a library is passing a string to a callback function, it is
very seldom the case that the callback assumes ownership of that
string and responsibility for its destruction.  Until we add traits
to annotate parameters to NativeCall (with regards to memory
management), I think it would be best to assume that callback strings
should *not* be freed