large objects and GC

[BCS]

Reply to Vladimir,

> This will be effectively the same as having a "wrapper" class for
> manually allocated memory. The class destructor, which will be called
> by the GC, should deallocate the external memory. The wrapper class
> should only have one field, and thus be very small and it will have
> the chance of leaking almost equivalent to the method you describe. I
> see no necessity for reference counting either, you just pass around
> the reference to the wrapper object.

I think this is based on the assumption that lots of systems only ever use 
the base pointer so why not let the programer leverage that?