Break chrome_initial's dependence on //components/startup_metric_utils/browser:lib

chrome/app/chrome_main_delegate.h

Index: chrome/app/chrome_main_delegate.h
diff --git a/chrome/app/chrome_main_delegate.h b/chrome/app/chrome_main_delegate.h
index 6751de27ff18ab7648d1f31f25f319a818137931..649ac59e1ec1cc11308f3011e41e4ba4741ef147 100644
--- a/chrome/app/chrome_main_delegate.h
+++ b/chrome/app/chrome_main_delegate.h
@@ -5,6 +5,8 @@
 #ifndef CHROME_APP_CHROME_MAIN_DELEGATE_H_
 #define CHROME_APP_CHROME_MAIN_DELEGATE_H_
 
+#include <stdint.h>
+
 #include <memory>
 
 #include "base/macros.h"
@@ -23,6 +25,9 @@ class CommandLine;
 class ChromeMainDelegate : public content::ContentMainDelegate {
  public:
   ChromeMainDelegate();
+  // |exe_entry_point_ticks| is the time at which the main function of the
+  // executable was entered, or 0 if not available.
+  explicit ChromeMainDelegate(int64_t exe_entry_point_ticks);

[fdoray, 2016/09/20 12:25:22]

I understand why it's more conservative to use int64_t in ChromeMain, but here I
would use base::TimeTicks. I prefer to put the value back in a TimeTicks as soon
as possible to minimize the amount of code where it's ambiguous how time is
represented.

[grt (UTC plus 2), 2016/09/20 19:20:26]

I like it. Done.

   ~ChromeMainDelegate() override;
 
  protected: