So is there some documentation on the "behavioral problems" their checker finds? If we know what to look out for, we can simply write some clippy lints to replicate the checks.
https://msdn.microsoft.com/en-us/library/windows/hardware/ff...
One of the more successful cases of research out of Microsoft Research making it into production use in regular-Microsoft.
I'm keeping the page in case I field Rust stuff as it's a nice list of things to look for. Not just for this tool but other developers applying CompSci solutions to Rust. They'll need a list of issues to encode in those.