I really had not thought this might be a problem, since ``nullptr`` represents a null pointer the best way possible. I might have made mistakes because I am not used to using allocator functions directly but I do not think ``nullptr`` can be a problem (``*alloc`` functions are part of the stl after all).