Fix coverage report not recording function usage

The following discussion from !125 (merged) should be addressed:

• @brandon.piotrzkowski started a discussion: (+1 comment)

  Not sure why the coverage report suddenly tanked down to almost nothing.

  Ran !126 (merged) with no code changes and has the same problem, so must be unrelated to this MR. My guess is that the code running and being checked are different, but this can be fixed in another MR at a later time.