Gees guys, you all have it wrong.
The real issue in an Intel issue, no the OS. And is caused/resolved by the BIOS.
In all computers, all components must be addressable in main memory or they cannot recieve data from the CPU. Most parts don't use much memory, but some use a lot. The Video card is one main culprit in most cases. Hard drive interfaces and other parts also take address space. So if you have a 512Megabyte video card, you are going to loose at least 512 Meg from your memory if you are using all 4 gig addressing space allowed by Intel chips in 32-bit mode. The video memory is mapped over the top of the RAM on your system, therefore lowering the amount of available memory to the OS. Some BIOS systems allow for 64-bit addressing outside of the OS, and can actively switch the memory addressing to allow a 32-bit OS to access all 4 gigabytes. This is was the Apple BIOS does when OSx is running on the machine. It is also seen on some systems running 32-bit Windows, but not all. It's all up to the BIOS.
When running a Microsoft OS on an Apple, the BIOS is virtualized in memory via Boot Camp and is only a 32-bit BIOS image. Therefore no re-mapping of video or other used memory is available. So the amount of RAM available to the OS is reduced. If anyone, you should blame this on Apple for not providing a BIOS under Boot Camp that can re-map higher memory to allow access to all 4 gigs of ram. 64-bit Windows versions will also have issues with 4 gig of RAM not showing if the BIOS does not allow for the re-mapping. Most laptop computers suffer from this problem, as they all seem to use 32-bit BIOSes only.
It's all due to the design made by Intel, and how good a BIOS is under your OS. Boot Camp's PC BIOS is to blame here.