Hi Niklas,
This does appear to be a bug. We are passing in the correct number of parameters but one of them is not named correctly. I'm not sure why it causes an error for you though, on my system SQL doesn't really care if the param name is correct as long as the number of params and the data types are correct. What version of MS SQL are you using?
I will correct this and try to get a patched release out soon.
Best,
Joe