Applications directory can not be properly derived if 32-bit binarycreator.exe is used to create an installer for a 64-bit application

On a Windows machine a 32-bit application is to be installed in "Program Files (x86)" and a 64-bit application is to go to "Program Files". My understanding is that to accomplish this, one is supposed to set the target directory in the config/config.xml file as

<TargetDir>@ApplicationsDir@/MyApp</TargetDir>

However, with this approach the installer has no way of knowing whether it is installing 32-bit or 64-bit application. My impression is that in the current implementation the ApplicationsDir takes into account the bit-ness of the installer and not the bit-ness of the application that is to be installed. This easily leads to incorrectly set target directory if one uses a 32-bit version of binarycreator.exe to create installer for e 64-bit application. It appears that the user should be able to specify explicitly in the config/config.xml file the bit-ness of the application to be installed and this is to be taken into account by the code in packagemanagercoredata.h when setting the Application directory.