If you notice, the space after GPT#3 is where your Bootcamp used to be. Because you have Recovery HD between OS X and Bootcamp, this would require delete recovery HD, merging the all of them to get OS X back, and re-installing OS X again (to get Recovery HD back).
Your MBR is fine.
If you want to see the same picture in Disk Utility, please see this link http://macs.about.com/od/usingyourmac/qt/Enable-Disk-Utilitys-Debug-Menu.htm. This will show you Recovery HD right after OS X and then the previous Bootcamp disk space.
This can also be done via diskutil commands as follows...
1. Merge Recovery HD into OS X. The order of disk0s2 and disk0s3 is very important otherwise you will lose all your OS X data.
diskutil mergePartitions JHFS+ "Macintosh HD" disk0s2 disk0s3
2. Now you can use Disk Utility to drag the Macintosh HD bottom left corner and make it full size. You have lost Recovery HD, but you can get it back by reinstalling OS X without touching any of your non-OS files.
diskutil mergePartitions
Usage: diskutil mergePartitions [force] format name
DiskIdentifier|DeviceNode DiskIdentifier|DeviceNode
Merge two or more pre-existing partitions into one. The first disk parameter
is the starting partition; the second disk parameter is the ending partition;
this given range of two or more partitions will be merged into one.
All partitions in the range, except for the first one, must be unmountable.
All data on merged partitions other than the first will be lost; data on the
first partition will be lost as well if the "force" argument is given.
If "force" is not given, and the first partition has a resizable file system
(e.g. JHFS+), it will be grown in a data-preserving manner, even if a different
file system is specified (in fact, your file system and volume name parameters
are both ignored in this case). If "force" is not given, and the first
partition is not resizable, you will be prompted if you want to erase.
If "force" is given, the first partition is always formatted. You should
do this if you wish to reformat to a new file system type.
Merged partitions are required to be ordered sequentially on disk.
See diskutil list for the actual on-disk ordering; BSD slice identifiers
may in certain circumstances not always be in numerical order but the
top-to-bottom order given by diskutil list is always the on-disk order.
Ownership of the affected disk is required.
Example: diskutil mergePartitions JHFS+ NewName disk3s4 disk3s7
This example will merge all partitions *BETWEEN* disk3s4 and disk3s7,
preserving data on disk3s4 but destroying data on disk3s5, disk3s6,
disk3s7 and any invisible free space partitions between those disks;
disk3s4 will be grown to cover the full space if possible.
