Renaming some files, making some changes to 64-bit build configuration and adding tests for calling assembly function with 0, 1, 2, 3, and 4 32-bit integer parameters without failure.

I have to pass the 5th, 6th, and above parameters on the stack.
Now calls 5 and 6 parameter functions successfully
Fixed assembly function that calls a c function with 0 or more functions.
Added tests for calling assembly function from an assembly function with up to 3 parameters.  This should not be able to handle 64-bit parameters, but that is next...
Before attempting to convert caller64.asm to support 8-byte parameters - for LPXLOPER/pointer types, which is what our plug-in currently should support in 64-bit mode.
Have to go back to the drawing board to figure out what should be happening.

64-bit Excel can use either XLOPER or XLOPER12
32-bit Excel can also use either XLOPER or XLOPER12

It all depends on if you have Excel 2007 and above, or below Excel 2007.

A 64-bit build will produce different parameter sizes for XLOPER, than a 32-bit build will.  So will a 64-bit build and a 32-bit build that uses the XLOPER12 data type.

Will 64-bit Excel call functions using XLOPER or XLOPER12? Will 32-bit Excel call functions using XLOPER or XLOPER12? I think it all depends on how easy we want it to be for the user.  I want our users to write a DLL that exposes functions with regular data types, not XLOPER data types.  I can convert all those types using Assembly to make sure the method is very optimized.

So users will write functions using types such as int, double, bool, std::string.  Have to think about this...