"Windows has triggered a breakpoint in imageBasics.exe" [SOLVED]

I've ran into an issue for my own project, and after trying to reproduce that issue I found it also happens with the imageBasics sample project.

When I run (running it from Visual Studio 10; MRPT.sln -> right click the sample project -> Debug -> Start new instance) this in Debug configuration, I get the following message:

"Windows has triggered a breakpoint in imageBasics.exe.

This may be due to a corruption of the heap, which indicates a bug in imageBasics.exe or any of the DLLs it has loaded.

This may also be due to the user pressing F12 while imageBasics.exe has focus.

The output window may have more diagnostic information."
The button "Break" and "Continue" are allowed to be pressed, but the "Ignore" is not.

When I just click Continue and keep press "Ignore" and "Continue" in the subsequent messages I get (grand total of about 9 messages, possibly 3 per image window Opened), I end up with the program actually in (what seems) working order. I get three image windows (win1, win2 and win3) with each an image loaded. When I close win3, the program terminates as it's supposed to do.

When I check the Debug Output log, I see to following:
* Messages related to loading all kinds of .dll files.
* Log messages about "HEAP[imageBasics.exe]: Invalid address specified to RtlValidateHeap( 02480000, 04590048 )", with text of the above described breakpoint message. There are 6 of these messages in total, with 3 unique RtlValidateHeap addresses (again, possibly related to the 3 image windows).
* A message about "The thread 'Win32 Thread' (0x2174) has exited with code 0 (0x0)."
* A message about a detected memory leak, followed by an 'object dump'
* The final message being "The program '[8488] imageBasics.exe: Native' has exited with code 0 (0x0)."
I've attached the full debug log in this thread, as I didn't want to flood this thread with a wall of text.

When running the Release configuration in the same way, I get pretty much the same story although no message about a memory leak.
I've also attached the full debug log in this thread for the Release version.

I've also tried running them using Command Prompt. Running the debug version gives me an Visual Studio 'Debug Assertion Failed' message box, while running the Release version gives me messages in the terminal that state that timeouts have happened while waiting for window creation:
"
Image loaded in 3.145ms
[WxSubsystem::createOneInstanceMainThread] Timeout waiting wxApplication to start up!
[CBaseGUIWindow:ctor] Timeout waiting window creation.
[CBaseGUIWindow:ctor] Timeout waiting window creation.
[CDisplayWindow::setPos] Window closed! win1
[CDisplayWindow::setPos] Window closed! win2
[CDisplayWindow::setPos] Window closed! win3
Press any key on 'win3' to exit
jpeg file save in 1.044
"

I've absolutely no clue what to make of this, but it seems to be related to CDisplayWindow, because that is also where I seem to have problems with in my own project. I have no issues with wxWidgets as I can run image related samples without any problems.
I'm building from an SVN checkout from 8-3-2011, and I'm very sure I didn't use the F12 button ;)

Thanks in advance,
Xilconic