The image below is vastly over simplified, but may clear up a couple things.

If the the OS is 32 bit, 4 Gig is all you have available to work with.
If the OS is 64 bit you can have more, but BiaB can only access the same as the 32bit OS, as it is a 32 bit app.
So No matter whether you have a 32 bit OS or 64bit OS, BiaB only uses the same amount as a 32 OS would on that system (we can argue all day on whether that is 3.5, 3.8 or 2.8 gig .. it is under 4 gig for sure). But being a 32 bit app BiaB only uses (and needs) under 4 gig, so no problem.

The issue is when a plugin is 64 bit (and you have a 64bit OS) Biab used to limit you to the 32bit memory limit, so the 64 bit app wouldn't run.
JBridge allows the 'plugin' to use more RAM, even though BiaB technically doesn't.
So it 'appears' as though BiaB has access to more RAM, but really it is the plugin that does. This is fine (since BiaB needs less than 4 gig of RAM to run itself; only additional plugins can raise it over that limit).

JBridge is not just a '3rd party solution'. It is integrated into BiaB and RB so it appears you are not using a 3rd party app .. it just loads the 64 bit plugin into the song and works. IMO this is what is meant by natively supported.

In a 64 bit OS I think it works like this:



Attached Files (Click to download or enlarge) (Only available when you are logged in)
JBridge=BBSimplified.jpg (47.18 KB, 74 downloads)
Make your sound your own!
.. I do not work here, but the benefits are still awesome