Suspension subclassing; CARSUSPENSIONINFO struct.

[fudje]

As hinted to in the Car graphics config thread ( http://vdrift.net/Forum/viewtopic.php?p=11414#11414 ), I have been working expanding the scope of suspension types simulation. Of particular interest to me is double wishbone suspension which some of you may realise cannot properly be simulated with a single hinge point, being described by an offset pair of additive sine curves (or, in other words, two circles, as opposed to the one that is available right now.

Anyway. For various reasons relating to doing things the "right" way, I'm trying to put this together with some supposedly straightforward polymorphism.
It now makes sense for CARDYNAMICS to contain not a vector of CARSUSPENSION but pointers there to (because you need pointers or references in C++ and you can't uses references like that). Easy to deal with — except that it buggers up the joeserialize stuff. I'm not entirely sure what joeserialize is supposed to achieve, but simpling preventing the suspension for being serialized doesn't seem to cause any problems.... Someone tell me if this is bad and will leak memory or something?
Moving on, I'm also interested in what the point of having a CARSUSPENSIONINFO struct is? In the interest of reducing the number of data types that need to be derived, is there a problem with storing that data directly in the CARSUSPENSION class (and derivates)?