[...]
This was OK .... until now when we have a new shared_ptr to deal with.
The real solution is to enhance the serialization API so that the code
used for implementing boost::shared_ptr can be applied to other
data types which are otherwise unserializable. Unfortunately, this
is a non-trivial task which I have yet to get to. So for now I
can't offer a real solution other than suggesting one use boost
shared pointer rather than std::shared_ptr. I dont' know if this
helps - but there it is.