I realized upon re-reading this, that you aren't the party responsible for allocating the object (or rather, at this point in the application logic, that knowledge seems to be abstracted away). That makes for a more complex problem, in which case I would probably go the same route you already have. To my knowledge, the only externally-predictable event upon object destruction is the calling of the DESTROY method (if it exists) within that class/package. There isn't (that I know of) a more universal hook point at which you can monitor general object disposal, simply for the sake of catching the few that you care about.

--rjray