Class deallocator not being called -- bug or oversight?

[Jarrett Billingsley]

"Jarrett Billingsley" <kb3ctd2 at yahoo.com> wrote in message 
news:fd8f6o$126d$1 at digitalmars.com...
>
> Something weird is going on.

Some more:

Calling GC.collect() changes nothing.

Adding the newly-allocated memory with GC.addRange() changes nothing, even 
if I then call GC.collect.

The spec says that "When a delete expression .. is executed, and f is a 
reference to a class instance that has a deallocator, the deallocator is 
called with a pointer to the class instance after the destructor (if any) 
for the class is called."  This is not happening, so I'm guessing this is a 
bug.