Seen this in Leyden profiles, but it is a generic issue. The profiles show Node::grow and VectorSet::grow as hot methods. The methods are small, and since they are implementing doubling-the-array scheme, we often exit early without actually growing.

Outlining the actual growing part from the capacity check would allow inlining the common case.