The PhiResolverState arrays are pre-sized to the maximum possible number of nodes that can be put into them, which when instrumenting turns out to be quite excessive. By not pre-sizing to the theoretical maximum I can measure a substantial improvements in calling methods (only a small fraction of calls ever have to grow the arrays from their default sizes), and a significant reduction of the total instructions executed in a variety of startup benchmarks