Document --collateral switch

[SkyLined]

It would be nice if BugId could try to allow the application to continue to run after issues such as use-after-frees or out of bounds reads by temporarily making the inaccessible memory accessible and filling it with a specific marker value. After the instruction that originally cause the AV has been executed without causing an AV this time, the memory should be restored to its original state and the application can continue.

This would allow you to get an idea of what you might be able to do when you can control the memory the application is incorrectly accessing.

[SkyLined]

This is working on my internal build, and turns out to be very useful when trying to determine exploitability of certain issues! :)

[SkyLined]

This has been released. Proper documentation is needed though.

[SkyLined]

There's information in the "usage" output of BugIc, so all that is left is a HOW-TO (see #66)