ambient-context

How to deal with cross-cutting concerns in a OO Application? Use Singleton? Dependency Injection? What?

Let's say that I'm currently designing an application where I will need to use a global timing system (it's a cross-cutting concern). I'll need to access data from that global timing system from basically anywhere in my app and it's not like I can see that "this part of the application will need it while the other won't". My question i...