Is this correct Timing behavior ?

Questions
1

I type this

Timing[Pause[1.0]]

and I get 0. for the time. I tried with all other possible expressions and the same holds. This seems to work in the OS X version we run at work.

2 
Timing[Pause[1.0]]

does not measure wall clock time, it measures CPU time spent in the kernel. Pause[] does not use much CPU time in the kernel at all (nothing to compute, just makes an OS call), so you get zero CPU time.
Try

AbsoluteTiming[Pause[1.0]]

which returns

{1.000627, Null}

Which returns wall clock time elapsed:

returning a list of the absolute number of seconds in real time that have elapsed

3

I reckon it was an unfortunate example, but if I replace Pause[1.0] with an actual computation, as in the examples from Timing—Wolfram Documentation it also does not work.

4

If the computations takes less that $TimeUnit, it will round to zero. Does this return zero on your system:

First@Timing[PrimeQ[Range[10^7]]]
5

The “quantum of time” is typically 16 mSec for Windows, but can change depending on what’s loaded.

6

Ok, whatever glitch happened with Timing, it is gone :-/ but I am still unable to use it in my program. See, what I attempt to do:

SetAttributes[MyTime, HoldAll];
MyTime[expression_, prefix_: "expression"] := 
  Block[{text = "Time for " <> prefix <> " is "}, Print["Starting"];
   Block[{aux2 = Timing[Evaluate[expression]]}, Print["Finished"];
    Print[text <> ToString[ aux2[[1]]*1000] <> "ms"]; aux2[[2]]]];

This always prints zero, no matter how long the computation in “expression” takes. Using AbsoluteTiming also does not work.