V668 There is no sense in testing the 'pNew' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlbase.h 8436
V668 There is no sense in testing the 'pUIAnimationCallbackDerived' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxanimationhelper.h 55
V668 There is no sense in testing the 'm_pSD' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 1064
V668 There is no sense in testing the 'pszRefDomain' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 1527
V668 There is no sense in testing the 'p' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 3429
V668 There is no sense in testing the 'p' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 3562
V668 There is no sense in testing the 'pMap' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 4220
V668 There is no sense in testing the 'pEnum' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 6410
V668 There is no sense in testing the 'pcd' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 6416
V668 There is no sense in testing the 'pEnum' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcom.h 6467
V668 There is no sense in testing the 'newBrush' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbrush.h 52
V668 There is no sense in testing the 'retimage' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbrush.h 382
V668 There is no sense in testing the 'argbs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbrush.h 623
V668 There is no sense in testing the 'argbs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbrush.h 653
V668 There is no sense in testing the 'pathData->Points' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluspath.h 140
V668 There is no sense in testing the 'pathData->Types' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluspath.h 146
V668 There is no sense in testing the 'argbs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluspath.h 1214
V668 There is no sense in testing the 'argbs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluspath.h 1250
V668 There is no sense in testing the 'argbs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluspath.h 1391
V668 There is no sense in testing the 'argbs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluspath.h 1424
V668 There is no sense in testing the 'newLineCap' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdipluslinecaps.h 157
V668 There is no sense in testing the 'nativeRegions' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusgraphics.h 1426
V668 There is no sense in testing the 'newRegion' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusregion.h 93
V668 There is no sense in testing the 'nativeFamilyList' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusfontcollection.h 68
V668 There is no sense in testing the 'newImage' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbitmap.h 340
V668 There is no sense in testing the 'bitmap' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbitmap.h 825
V668 There is no sense in testing the 'bitmap' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. gdiplusbitmap.h 868
V668 There is no sense in testing the 'm_Data' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. comutil.h 377
V668 There is no sense in testing the 'm_Data' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. comutil.h 396
V668 There is no sense in testing the 'newData' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. comutil.h 415
V668 There is no sense in testing the 'm_Data' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. comutil.h 568
V668 There is no sense in testing the 'm_Data' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. comutil.h 580
V668 There is no sense in testing the 'm_Data' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. comutil.h 602
V668 There is no sense in testing the 'mask' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxdrawmanager.cpp 2303
V668 There is no sense in testing the 'pGroup' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxribboninfo.cpp 1262
V668 There is no sense in testing the 'pParser' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxribboninfo2.cpp 409
V668 There is no sense in testing the 'pBtnBack' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxtaskspane.cpp 4055
V668 There is no sense in testing the 'pBtnForward' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxtaskspane.cpp 4067
V668 There is no sense in testing the 'pButton' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. afxtaskspane.cpp 4087
V668 There is no sense in testing the 'm_pBuffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 1095
V668 There is no sense in testing the 'm_pBuffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 1125
V668 There is no sense in testing the 'm_pAccessorInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 1227
V668 There is no sense in testing the 'pBinding' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 2712
V668 There is no sense in testing the 'm_pfClientOwnedMemRef' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 2719
V668 There is no sense in testing the 'pObject' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 2834
V668 There is no sense in testing the 'pObject' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 2873
V668 There is no sense in testing the 'm_pBuffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 2960
V668 There is no sense in testing the 'pBinding' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 3269
V668 There is no sense in testing the 'm_pfClientOwnedMemRef' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 3276
V668 There is no sense in testing the 'm_pBuffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 3439
V668 There is no sense in testing the 'pBinding' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 3797
V668 There is no sense in testing the 'pObject' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 3814
V668 There is no sense in testing the 'm_pBuffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 3865
V668 There is no sense in testing the 'm_pParameterBuffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4453
V668 There is no sense in testing the 'm_pParameterEntry' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4475
V668 There is no sense in testing the 'm_ppParamName' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4480
V668 There is no sense in testing the 'm_pEntry' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4548
V668 There is no sense in testing the 'm_pParameterEntry' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4574
V668 There is no sense in testing the 'm_pParamInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4823
V668 There is no sense in testing the 'pAccessorInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4896
V668 There is no sense in testing the 'm_pXMLAccessor' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4944
V668 There is no sense in testing the 'm_pXMLAccessor' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 4971
V668 There is no sense in testing the 'm_phRow' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldbcli.h 5877
V668 There is no sense in testing the 'pBrowserSite' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dlgdhtml.cpp 705
V668 There is no sense in testing the 'pFilter' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dlgfile.cpp 368
V668 There is no sense in testing the 'lpwstrFilter' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dlgfile.cpp 383
V668 There is no sense in testing the 'lpwstrFilter' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dlgfile.cpp 396
V668 There is no sense in testing the 'm_ppBins' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcoll.h 2608
V668 There is no sense in testing the 'ppBins' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlcoll.h 2939
V668 There is no sense in testing the 'pstrCanonicalizedURL' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 166
V668 There is no sense in testing the 'pRet' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2035
V668 There is no sense in testing the 'm_pNextInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2463
V668 There is no sense in testing the 'm_pFoundInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2533
V668 There is no sense in testing the 'm_pNextInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2612
V668 There is no sense in testing the 'm_pNextInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2631
V668 There is no sense in testing the 'm_pFoundInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2635
V668 There is no sense in testing the 'm_pFoundInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. inet.cpp 2660
V668 There is no sense in testing the 'pProp' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. olepset.cpp 859
V668 There is no sense in testing the 'pSect' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. olepset.cpp 1356
V668 There is no sense in testing the 'pSect' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. olepset.cpp 1444
V668 There is no sense in testing the 'pInputs' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. wincore.cpp 1624
V668 There is no sense in testing the 'pEntry' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlwin.h 3034
V668 There is no sense in testing the 'pAccel' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlctl.h 1843
V668 There is no sense in testing the 'pBytes' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlctl.h 3923
V668 There is no sense in testing the 'm_pCUtlPropInfo' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldb.h 1691
V668 There is no sense in testing the 'pRow' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atldb.h 8734
V668 There is no sense in testing the 'pRoot' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlevent.h 463
V668 There is no sense in testing the 'm_pObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 2582
V668 There is no sense in testing the 'm_pInheritedObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 2589
V668 There is no sense in testing the 'm_pObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 2624
V668 There is no sense in testing the 'm_pInheritedObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 2640
V668 There is no sense in testing the 'm_pObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 3109
V668 There is no sense in testing the 'm_pInheritedObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 3116
V668 There is no sense in testing the 'm_pObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 3151
V668 There is no sense in testing the 'm_pInheritedObjectType' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 3167
V668 There is no sense in testing the 'm_pRevert' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 5118
V668 There is no sense in testing the 'm_pRevert' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 5155
V668 There is no sense in testing the 'm_pRevert' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 5191
V668 There is no sense in testing the 'm_pRevert' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 5231
V668 There is no sense in testing the 'm_pRevert' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsecurity.h 5254
V668 There is no sense in testing the 'pInfo->m_pStrToolTip' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. atlsnap.h 1485
V668 There is no sense in testing the 'p' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dxtmpl.h 127
V668 There is no sense in testing the 'pNewData' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dxtmpl.h 342
V668 There is no sense in testing the 'pNewData' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dxtmpl.h 399
V668 There is no sense in testing the 'm_pHashTable' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. dxtmpl.h 1130
V668 There is no sense in testing the 'pNewFileDesc' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. mapiunicodehelp.h 99
V668 There is no sense in testing the 'pNewRecipDesc' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. mapiunicodehelp.h 145
V668 There is no sense in testing the 'pMessageOut' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. mapiunicodehelp.h 405
V668 There is no sense in testing the 'm_pData' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. spcollec.h 270
V668 There is no sense in testing the 'pNewData' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. spcollec.h 329
V668 There is no sense in testing the 'pszOptAttribsVendorPref' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. sphelper.h 1019
V668 There is no sense in testing the 'pNode' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. speventq.h 782