Roll Chrome into Mojo.

ui/events/latency_info.cc

Index: ui/events/latency_info.cc
diff --git a/ui/events/latency_info.cc b/ui/events/latency_info.cc
index 9b186a8f0a65a793259cecf72564a93166b4d9d3..248acb932f05ac2735672eb3e84ea6d05ededafa 100644
--- a/ui/events/latency_info.cc
+++ b/ui/events/latency_info.cc
@@ -202,7 +202,7 @@ void LatencyInfo::AddLatencyNumber(LatencyComponentType component,
                                    int64 id,
                                    int64 component_sequence_number) {
   AddLatencyNumberWithTimestamp(component, id, component_sequence_number,
-                                base::TimeTicks::HighResNow(), 1);
+                                base::TimeTicks::Now(), 1);
 }
 
 void LatencyInfo::AddLatencyNumberWithTimestamp(LatencyComponentType component,
@@ -239,7 +239,7 @@ void LatencyInfo::AddLatencyNumberWithTimestamp(LatencyComponentType component,
         // CrOS). So we need to adjust the diff between in CLOCK_MONOTONIC and
         // CLOCK_SYSTEM_TRACE. Note that the diff is drifting overtime so we
         // can't use a static value.
-        int64 diff = base::TimeTicks::HighResNow().ToInternalValue() -
+        int64 diff = base::TimeTicks::Now().ToInternalValue() -
             base::TimeTicks::NowFromSystemTraceTime().ToInternalValue();
         ts = component.event_time.ToInternalValue() - diff;
       } else {