Steve, yes, I believe the TestGeneratorScript is the right tool for what you're trying to do. You should spend some time getting familiar with it and building a script that's complex enough to reflect how you believe the application will be used.
What you should be meassuring is CPU and memory consumption (by using windows performance monitor) and response times that will be logged by the tool.
You can test 10 sessions running at the same time by configuring that in the tool. I believe that will be fairly similar as 10 different users, but if you actually want to test 10 different users then just run the script from 10 different PCs at the same time logged with 10 different users.
Decent link here including a link to the load simulator dashboard which will give you a very rough approximation as to CPU\ memory usage : http://community.qlik.com/message/83460#83460
I went through a similar process as yourself - discounted jmeter due to the time it would take to learn and configure, discounted engaging with a reseller to implement HP LoadRunner for us to simulate 500 users due to price. If our dashboards were accessible to the internet I would have investigated a few SaaS load testing offerings out there but they're not, so I didn't
For a down and dirty quick approximation try the load simulator dashboard. I've tried it on v10 SR5 and works ok.
If you find anything cheap and quick let me know
Thanks for the advice - due to time my actual solution was fairly crude (similar to Daniel Rozental's suggestion). :-)
As I was 'only' load-testing for 10 Users - I just got 10 colleagues to log-on to the Dashboard and click for all their worth! I set Windows Performance Monitor away in the background (http://www.windowsnetworking.com/articles_tutorials/windows_2003_performance_monitor.html), and recorded the results.
This very closely (if not exactly) mimicked a worst-case scenario - and, as it happens, it looks as though the server will be able to cope :-)
I also had a play around with fugusona's suggestion - and, although I'm not sure I was using it to its full potential - it also suggested that the Server would always be within its "Effective RAM" threshold... so I'm fairly confident we should be OK.
Obviously if I was going to be load-testing more than 10 Users I would look more closely into the TestGeneratorScript solution.