Various utility methods in ParseUtil are exercised on startup in various applications, via URLClassPath and other.

Analyzing startup profiles on some internal applications and then running some experiments I've been able to find a few small improvements that together reduce bytecode executed in ParseUtil from ~4% of the total to ~2.7% of the total, with a ~1.2% reduction in total bytecode executed.