Added null check on init

This fixed the issue I was having when destroying a datatable with a certain number of columns (set through the "columns" property when initializing).  `col` was null in cases where the second table that was generated had less columns that the one before.

For more info I initially described the problem [here](http://www.datatables.net/forums/discussion/20524/destroy-issue).