Override for types that need access to a PointerTable in order to destroy frozen data WARNING! Frozen data may have deduplicated portions, so it's possible that a given object may have multiple references Any attempt to cleanup/destroy frozen data must take care to safely allow DestroyObject to be called multiple times on the same frozen object Generally speaking, it's NOT safe to invoke the built-in destructor multiple times