> There's virtually no sensible case where the person calling free() doesn't know the size of the allocation

We already have enough memory-unsafety bugs going around without making free() more difficult to use correctly as well.