Pro Open source code
The source code is open to review. It has already had a security audit and it did well, with small problems fixed by authors within days of being reported. Its predecessor source, Truecrypt, had a detailed audit that found its capabilities sound, completed (ironically) shortly before the TC folks decided to call it quits. Anyone skeptical or curious about what it does can see how it works, at the gut level.
Pro Support for AES code in CPU
Most Intel and AMD (and possibly other) CPUs have AES specific instruction sets, so you needn't task the CPU during the en/de/crypt process when using AES, VC throughput is as if the code were in 'firmware'; you can see the effect if you choose anything but AES as your cipher.
Con Not plug and play
Requires some tech savvy, so some skill is required, particularly if things go wrong. In the Windows world different UEFI implementations can cause problems in one, not in others, and the solutions are not uniform between issues. For Bitlocker, Microsoft worked out issues with vendors before hand, so if Windows installs and works without bitlocker, it will likely work with it.