I found the answer here. It says
In SQL Server
2005 and later, the SQL Server
Profiler graphical user interface
displays the Duration column in
milliseconds by default, but when a
trace is saved to either a file or a
database table, the Duration column
value is written in microseconds
I was watching them after saving the trace file in database.