Sql Management Objects Scripting Bugs

A couple bugs I've noticed when using the Sql Management Objects Scripter class.

• SMO does not generate default constraints inline, but instead generates an ALTER TABLE script. More details here.
• When passing an array of SqlSmoObjects to Scripter.Script() with the option "IncludeHeaders" turned on, it is not ordering the scripts correctly. Any ALTER scripts are not ordered under the header for the object they belong to, and are instead listed at the end of the scripts. This is very problematic if you're trying to keep the scripts for a given object together.