Consider a (recursive?) creation context tracker

When an object is created by passing an existing C type, require a creation context string be passed which would be stored on the object. That way, once an object is freed, it would print out what its creation context was, so memory leaks would be easier to track.

The issue names no files, tests, or entry points. Start by locating where existing C types become objects and where those objects are freed, then determine how a creation context could be propagated and reported; done means freed objects identify their creation context without disrupting current ownership behavior.

Written by the indexing model from the issue text.