Improve accuracy of application start up time in docker

Today it's impossible to compare application start-up time between docker and non-docker hosted apps. The docker-hosted startup time includes the time to start the container.

For example, comparing a .NET app to a go app in docker:
I'm pretty sure the go app should start faster than the .NET app, but the current numbers indicate the reverse.

Is there a way to make these app types more comparable?

One idea: write to the console as we do with ready-state text. The docker container could use CMD + bash to write to the console to indicate that the docker container has finished starting, then launch the docker-hosted app. Crank uses that console write to remove the docker container start time from the app startup time.