The TimeLivenessAnalysis develop flag can be used to "profile" time spent doing method liveness analysis, which might have been useful during its inception but unlikely since.

To boot, the implementation leaves a few breadcrumbs in release/product builds that might actually add a bit of overhead:
- a number of unused static elapsedTimers
- TraceTime calls wrapping various phases - these constructors are not inlineable so the calls are not optimized away (but at least they don't issue any calls to get the actual time)

Removing or ifdef:ing out these has a small effect on generated code size.

I propose removing the flag and the timing code, alternatively cleaning up so all timing related code is ifdef'ed away.