New feature: getting a stack trace on leaked objects with VTK_DEBUG_LEAKS

Well it’s not all that sad :slight_smile:

I’m not sure why vtkCommand and subclasses use that other version of vtkDebugLeaks::ConstructClass. It should work just as well to use vtkDebugLeaks::ConstructClass(vtkObjectBase* object).