So how come the fast allocator is dll bound and the default isn't ? :O
Okay okay, I'll make a guess, and you guys can tell me whether it's right or wrong.
Is it because that the default allocator locally defines the internal methods so that calls to this allocator will lead to local code space located calls to the new and delete operators? And that the fast allocator makes calls to the new and delete operators explicitly within the primary methods (allocate, deallocate), for whom the calls to the new and delete operators are directed to local code space that belongs to the caller's module, so in turn the calls are bound to the caller's module and that an attempt to call the fast allocator's methods from a dll will only invoke the code located in the module of the caller? Sorry, reiterated unintentionally, but makes it more clearer.