Preview of contribution / More .ini APIs (nearly completes set of PrivateProfile API)

To extend and nearly complete Win32's PrivateProfile API, our company likes to contribute these missing mappings. The code origins from a commercial project and was backported into JNA with respect to your licence. We send this preview, because we have the following problems and like to get your opinion how to go on now:
* Rewritten from Java 7 to Java 6: The code origins from Java 7 and we have rewritten it to Java 6. The original code worked perfectly in our commercial product, but we are not certain whether we did a (possibly hidden) mistake when rewriting it for Java 6. As we already spend one day for writing the code from scratch again, we hope that you don't mind that we want you to double-check that it looks "correct" on Java 6.
* Use of JUnit 4.11 including Hamcrest. The original code was tested using Java 4.11 including Hamcrest. Hence, all tests we provide do not compile in the JNA environment. Be assured, they all pass in the original environment, so actually you could just throw them away ;-) but certainly this is neither a professional or safe option. As we do not have any more sponsored time for "backporting" for really outdated JUnit 3.8.1 or getting rid of Hamcrest, we have provided the needed libraries as markers in the lib folder and kindly ask to migrate JNA to 4.11 -- as it makes contributing to JNA so much easier. See, we are currently refactoring many more contributions from our original code to the JNA environment, and all that tests are using JUnit 4.11 / Hamcrest, so sticking with 3.8.1 means either dropping the tests or investing days into rewrites (which WE don't have any benefit of).
* Can neither build nor test. As described in the discussion forum, we are not able to build or test JNA, so we contributed this preview "blindly". The reason is that we must not invest the time and space to install Cygwin and configure everything else needed, just to be able to ensure that code we give away for free actually runs in that particular environment. We hope that you understand that our company invested real money in the development of that code, and that it is only fair that if you insist on a build system that makes it more harder to build and test than simply typing "mvn test", then our company is not willing to invest any additional time for Cygwin, but just gives you the code "as-is".

We're hopeing that you find a wise and fair answer, so we can go on and contribute more of our commercially developed code to the JNA open source project. Please understand that days of backports / rewrites are out of scope of our sponsored budget for the JNA project, but one the other hand, we really would love to give away all that code we developed in the past to the JNA project.

Please also note that more contributions are ready to get previewed, but as they also are done using Junit 4.11 / Hamcrest, and as they depend on the APIs provided in THIS pull request, it makes no sense to contribute them before we received an answer that technically allowes us to technicall provide a mergable pull request.