So what exactly is coming with extended C++ support?

[Sean Kelly via Digitalmars-d]

On Tuesday, 30 September 2014 at 21:19:44 UTC, Ethan wrote:
>
> With a codebase like ours (mostly C++, some D), there's a few 
> things we need. Deterministic garbage collection is a big one - 
> when our C++ object is being destroyed, we need the D object to 
> be destroyed at the same time in most cases. This can be 
> handled by calling GC.collect() often, but that's where the 
> next thing comes in - the time the GC needs. If the time isn't 
> being scheduled at object destruction, then it all gets lumped 
> together in the GC collect. It automatically moves the time 
> cost to a place where we may not want it.

Would delete on the D side work here?  Or the more current
destroy()?  ie. is release of the memory a crucial part of the
equation, or merely finalization?