This doesn't represent accurate or useful information
It was just the total time divided by the count
of decorated methods

For example copying the raw data to excel
allow for easier formatting sorting and
other math operations

This does not happen while debugging with Chrome, which is what I used
for the most of the time and never noticed the issue

Since the update for Reanimated 2 (TurboModules/JSI)
It's no longer possible to use the old (Chrome) debugging flow
I've discovered the timing information was not at all relative to
app launch, the duration between start/end is correct but the
start/end values are otherwise useless if they display like 8468.7min
To be useful they need to be relative to app launch time

Since timing otherwise works correct, we can capture an offset - APP_LAUNCH_TIME
and subtract this value from the timings we make to capture a correct
start/end time relative to APP_LAUNCH_TIME