Description:
------------
The output is inconsistent with the output from executing the same query using the mssql extension (see expected result section for details).

Test script:
---------------
<?php

if (!extension_loaded('pdo_dblib')) {
    die('skip not loaded');
}
require dirname(__FILE__) . '/config.inc';

$stmt = $db->prepare('SELECT 1, 2 AS named, 3');
$stmt->execute();
var_dump($stmt->fetch());


Expected result:
----------------
The mssql extension starts "computed" names at "computed" and uses a sequence to name subsequent columns, not the column number:
https://github.com/php/php-src/blob/PHP-5.6.19/ext/mssql/php_mssql.c#L1225

In this case, the first column should be "computed" and the third should be "computed1."

Additionally, debug mode should not be reporting memory leaks.

Actual result:
--------------
---------------------------------------
/vagrant/pdo_dblib-clean/dblib_stmt.c(106) : Block 0x00000000 status:
NULL
---------------------------------------
array(6) {
  ["computed0"]=>
  string(1) "1"
  [0]=>
  string(1) "1"
  ["named"]=>
  string(1) "2"
  [1]=>
  string(1) "2"
  ["computed2"]=>
  string(1) "3"
  [2]=>
  string(1) "3"
}
[Thu Feb 25 23:04:41 2016]  Script:  '/vagrant/pdo_dblib-clean/tests/timeout.php'
/home/vagrant/php-src/main/spprintf.c(245) :  Freeing 0x7F1E9FB6B518 (79 bytes), script=/vagrant/pdo_dblib-clean/tests/timeout.php
Last leak repeated 1 time
[Thu Feb 25 23:04:41 2016]  Script:  '/vagrant/pdo_dblib-clean/tests/timeout.php'
/vagrant/pdo_dblib-clean/dblib_stmt.c(211) :  Freeing 0x7F1E9FB6D270 (6 bytes), script=/vagrant/pdo_dblib-clean/tests/timeout.php
=== Total 3 memory leaks detected ===