No, I get it, but I mean transparent so that stdlib malloc and free could be used. I understand it's not probably feasible.
You'd never be able to make it just a drop in replacement, because it's not just about the allocation and freeing. The interesting stuff is specifying the hierarchies so that freeing a higher object frees lower ones too. Existing code using malloc/free wouldn't be doing that.
You could use LD_PRELOAD to load a library that does the replacement[1].
[1] http://stackoverflow.com/a/10008252
Actually, it is almost too transparent for C programmers:
>> From the programmer's point of view, the talloc context is completely equivalent to a pointer that would be returned by the memory routines from the C standard library.