In any abstract allocation, it is entirely possible that the place the object is freed has little knowledge of how it was created. This is object abstraction at it's basic definition.

I don't do that; I like to have the allocation and free in the same code module so I can ensure there's no leak, double deletion, null deletion etc. But I know it happens, routinely. In a library for instance.