CBC executable wallclock output not matching actual solver time

[SouthernGuy89]

I'm prototyping an application that generates MIP and calls the CBC executable. It's slow and I'm getting inconsistent information about the time spent in the CBC solver. So I'm trying to see if there's something I'm doing wrong in my own code or if the executable has some overhead that is underreported by its own wall clock output.

Problem: The executable consistently reports wallclocks times < 100 ms when solving my probvem. However, when isolate the code for launching the process and waiting for it to finish, I get readings of 700-800 ms. Is this just some overhead of the solver that's not being counted in the solving time or is there another issue?

I considered the overhead of starting a new process as a factor but for comparison launching cmd.exe in my code takes ~10 ms. So this seems likely an unlikely explanation for the response time.