Expose the sandbox related code through the content API. I did a bit of cleanup while I was doing...

chrome/test/base/chrome_test_suite.cc

Index: chrome/test/base/chrome_test_suite.cc
===================================================================
--- chrome/test/base/chrome_test_suite.cc	(revision 107845)
+++ chrome/test/base/chrome_test_suite.cc	(working copy)
@@ -6,7 +6,6 @@
 
 #include "base/command_line.h"
 #include "base/file_util.h"
-#include "base/mac/scoped_nsautorelease_pool.h"
 #include "base/memory/ref_counted.h"
 #include "base/metrics/stats_table.h"
 #include "base/path_service.h"
@@ -31,6 +30,7 @@
 
 #if defined(OS_MACOSX)
 #include "base/mac/mac_util.h"
+#include "base/mac/scoped_nsautorelease_pool.h"
 #include "content/common/chrome_application_mac.h"
 #endif
 
@@ -159,10 +159,9 @@
 void ChromeTestSuite::Initialize() {
 #if defined(OS_MACOSX)
   chrome_application_mac::RegisterCrApp();
+  base::mac::ScopedNSAutoreleasePool autorelease_pool;
 #endif
 
-  base::mac::ScopedNSAutoreleasePool autorelease_pool;
-
   base::TestSuite::Initialize();
 
   chrome::RegisterChromeSchemes();