Revert of sandbox: Fix Win64 porting issue by using SIZE_T instead of ULONG

Revert of sandbox: Fix Win64 porting issue by using SIZE_T instead of ULONG (patchset #3 id:40001 of https://codereview.chromium.org/921353002/)

Reason for revert:
Speculative revert after discussion on IRC, this seems pretty unlikely but may have caused the failures at:

http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/35506

Original issue's description:
> sandbox: Fix some nt_internals.h function prototypes for Win64
>
> NtQuerySection should use ULONG instead of SIZE_T as it is dealing with PE section sizes.
>
> NtQueryVirtualMemory should use SIZE_T instead of ULONG as it is dealing with memory sizes.
>
> DynamoRIO, another project that consumes these native APIs, uses the prototypes introduced by this change.
>
> R=robertshield@chromium.org,rvargas@chromium.org
> BUG=458690
>
> Committed: https://crrev.com/4ede4e174a51d08262edfb2e2c05845504bd9b1a
> Cr-Commit-Position: refs/heads/master@{#317177}

TBR=jschuh@chromium.org,robertshield@chromium.org,thakis@chromium.org,wfh@chromium.org,rvargas@chromium.org,rnk@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=458690
Committed: https://crrev.com/faeb8f6a5524dded1f97c16dee4b09dce548bae4
Cr-Commit-Position: refs/heads/master@{#317409}

[JF, 2015-02-20 21:45:17]

Created Revert of sandbox: Fix Win64 porting issue by using SIZE_T instead of
ULONG

[commit-bot: I haz the power, 2015-02-20 21:46:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/943043002/1

[commit-bot: I haz the power, 2015-02-20 21:47:05]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-20 21:47:57]

Patchset 1 (id:??) landed as
https://crrev.com/faeb8f6a5524dded1f97c16dee4b09dce548bae4
Cr-Commit-Position: refs/heads/master@{#317409}

[JF, 2015-02-20 21:51:14]

I should have added:
BUG= https://code.google.com/p/chromium/issues/detail?id=460563

[JF, 2015-02-21 02:08:49]

The build was fixed after this revert:
  http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20(dbg)(1)

Specific build:
 
http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%28...

I'm calling this CL the culprit :-)