always operate on running_count atomically when multithreaded

In upcoming changes we'll need to read running_count within error() to determine
whether we're single threaded or not. To do this while avoiding torn reads, we
need to use atomic reads and writes with running_count.

Github: related to #131 "minimal trace mode"